The Tanium application must install security-relevant software updates within the time period directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-254949	TANS-AP-001215	SV-254949r961683_rule		Medium

Description
Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period utilized must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

Description

Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions that are used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers today provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period utilized must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs).

STIG	Date
Tanium 7.x Application on TanOS Security Technical Implementation Guide	2024-06-04

Details

Check Text ( C-58562r867745_chk )
Ensure all components of the Tanium application have been updated within 60 days of the vulnerability being announced by Tanium. Critical Vulnerabilities must be updated within 30 days. --- Consult with the Tanium System Administrator to review the documented time window designated for updates. If a window of time is not defined, or does not specify a reoccurring frequency, this is a finding. 1. Using a web browser on a system that has connectivity to the Tanium Application, access the Tanium Application web user interface (UI) and log on with multi-factor authentication. 2. Click "Administration" on the top navigation banner. 3. Under "Configuration," select "Solutions". If any module has the text, "Update to" a newer (greater) version number compared to the Installed version number in the Tanium Modules section of the page, this is a finding. If the Tanium application is an "airgap" installation, work with the Tanium Technical System Administrator to determine if the modules are up to date.

Check Text ( C-58562r867745_chk )

Ensure all components of the Tanium application have been updated within 60 days of the vulnerability being announced by Tanium. Critical Vulnerabilities must be updated within 30 days.
---
Consult with the Tanium System Administrator to review the documented time window designated for updates.

If a window of time is not defined, or does not specify a reoccurring frequency, this is a finding.

1. Using a web browser on a system that has connectivity to the Tanium Application, access the Tanium Application web user interface (UI) and log on with multi-factor authentication.

2. Click "Administration" on the top navigation banner.

3. Under "Configuration," select "Solutions".

If any module has the text, "Update to" a newer (greater) version number compared to the Installed version number in the Tanium Modules section of the page, this is a finding.

If the Tanium application is an "airgap" installation, work with the Tanium Technical System Administrator to determine if the modules are up to date.

Fix Text (F-58506r867746_fix)
Consult with the Tanium System Administrator to review the documented time window designated for updates. If a window of time is not defined, or does not specify a reoccurring frequency, work with the Tanium Administrator to document. 1. Using a web browser on a system that has connectivity to the Tanium Application, access the Tanium Application web user interface (UI) and log on with multi-factor authentication. 2. Click "Administration" on the top navigation banner. 3. Under Configuration, select "Solutions". If any module has the text, "Update to" a newer (greater) version number compared to the Installed version number in the Tanium Modules section of the page, work with the Tanium Administrator to update those modules or content. If the Tanium application is an "airgap" installation, work with the Tanium Technical System Administrator to determine if the modules are up to date.

Fix Text (F-58506r867746_fix)

Consult with the Tanium System Administrator to review the documented time window designated for updates.

If a window of time is not defined, or does not specify a reoccurring frequency, work with the Tanium Administrator to document.

1. Using a web browser on a system that has connectivity to the Tanium Application, access the Tanium Application web user interface (UI) and log on with multi-factor authentication.

2. Click "Administration" on the top navigation banner.

3. Under Configuration, select "Solutions".

If any module has the text, "Update to" a newer (greater) version number compared to the Installed version number in the Tanium Modules section of the page, work with the Tanium Administrator to update those modules or content.

If the Tanium application is an "airgap" installation, work with the Tanium Technical System Administrator to determine if the modules are up to date.